Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

modify the sync numbers of 'start_sync' function #5869

Merged
merged 1 commit into from
Oct 3, 2018

Conversation

RootkitKiller
Copy link
Contributor

if the 'known_trx.mode' of the 'notice_message' is 'last_irr_catch_up', should use 'known_trx.pending' instead of 'known_blocks_pending'. because the blocks of 'known_blocks_pending' needs to be verified.

@RootkitKiller RootkitKiller changed the base branch from master to develop September 30, 2018 14:01
@RootkitKiller
Copy link
Contributor Author

What is the cause of the problem that 'Some checks were not successful
2 failing and 6 successful checks'?

Copy link
Contributor

@wanderingbort wanderingbort left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the next person who reviews, please note that non-adversarial input when both known_blocks and known_trx mode == last_irr_catchup should also have the peer's LIB number in known_trx.pending and the peer's head block number in known_blocks.pending . This makes the target of the sync the peer's LIB which is "correct"

@spoonincode
Copy link
Contributor

1.3.x?

@heifner
Copy link
Contributor

heifner commented Oct 2, 2018

@spoonincode @wanderingbort and I discussed 1.3.x for this. It is a bit obscure. I'm good with either 1.3.x or develop. Thoughts?

@spoonincode
Copy link
Contributor

I didn't actually study the change closely. If you & bart already think it's obscure enough to wait for 1.4 I've got no beef -- just wanted to make sure we considered it

@heifner heifner merged commit 644473e into EOSIO:develop Oct 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants